New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add 'only_transfers_as_changes' option to synchronize module #57885
add 'only_transfers_as_changes' option to synchronize module #57885
Conversation
The test
The test
The test
The test
The test
The test
The test
The test
|
The test
The test
|
The test
|
Thank you very much for your interest in Ansible. Ansible has migrated much of the content into separate repositories to allow for more rapid, independent development. We are closing this issue/PR because this content has been moved to one or more collection repositories.
For further information, please see: |
SUMMARY
This change adds a new option 'only_transfers_as_changes' to the synchronize module.
Rationale
When managing configurations to be deployed with ansible in git the time stamps of the files aren't preserved. When working with a distributed team this means time stamps of config files are always local to the member's computers. This together with the usage of the synchronize module often results in ansible detecting changes where there actually aren't any and in consequence unnecessary restarts of services at deploy time - often services the person wasn't even working on.
This PR adds a new boolean option 'only_transfers_as_changes' to the synchronize module that does the following:
While setting the 'checksum' option may have an impact on synchronize's performance this should be negligible considering the main use would be for relatively small text files.
ISSUE TYPE
COMPONENT NAME
sychronize
ADDITIONAL INFORMATION